This PR updates the release.yml GitHub Actions workflow to trigger on the labeled event for pull requests. This allows the workflow to be re-run when a label, such as deps-reviewed, is added to a PR, ensuring that processes like dependency checks are re-evaluated after manual approval.

Files Changed Analysis

• .github/workflows/release.yml: Modified to add labeled to the list of pull request types that trigger the workflow. This is a single-line configuration change.

Architecture & Impact Assessment

• Accomplishment: The change enables the release workflow to react to labeling events on a pull request, integrating a manual review step (labeling) with the automated CI/CD pipeline.
• Key Technical Changes: The on.pull_request.types array in the workflow's trigger configuration was expanded from [opened, synchronize, reopened] to [opened, synchronize, reopened, labeled].
• Affected System Components: This change directly affects the repository's CI/CD release process managed by GitHub Actions. The primary impact is on the conditions that trigger the release workflow.

Here is a visualization of the trigger change:

graph TD
    subgraph Before
        A[PR Opened] --> B{Release Workflow};
        C[PR Synchronized] --> B;
        D[PR Reopened] --> B;
    end
    subgraph After
        A2[PR Opened] --> B2{Release Workflow};
        C2[PR Synchronized] --> B2;
        D2[PR Reopened] --> B2;
        E2[PR Labeled] --> B2;
    end

Scope Discovery & Context Expansion

• The change is isolated to the workflow trigger configuration. However, its functional impact relates to the entire process orchestrated by the release.yml workflow. Based on the PR description mentioning dep-guard and the deps-reviewed label, this workflow is likely responsible for security and dependency validation before a release. By triggering on the labeled event, the workflow can now proceed after a required manual dependency review is marked as complete via labeling.

Powered by Visor from Probelabs

Last updated: 2026-04-17T13:59:57.264Z | Triggered by: pr_opened | Commit: bf9fd9b

💡 TIP: You can chat with Visor using /visor ask <your question>

Security Issues (1)

  release:
    if: github.event_name == 'push' && github.ref == 'refs/heads/master'
    needs: [linter, test]
    runs-on: ubuntu-latest

Security Issues (1)

  release:
    if: github.event_name == 'push' && github.ref == 'refs/heads/master'
    needs: [linter, test]
    runs-on: ubuntu-latest

Performance Issues (1)

if: github.event.action != 'labeled' || github.event.label.name == 'deps-reviewed'

Powered by Visor from Probelabs

Last updated: 2026-04-17T13:59:29.494Z | Triggered by: pr_opened | Commit: bf9fd9b

💡 TIP: You can chat with Visor using /visor ask <your question>

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

🚨 Jira Linter Failed

Commit: bf9fd9b
Failed at: 2026-04-17 16:49:36 UTC

The Jira linter failed to validate your PR. Please check the error details below:

failed to get Jira issue: failed to fetch Jira issue TT-16977: Issue does not exist or you do not have permission to see it.: request failed. Please analyze the request body for more details. Status code: 404

Next Steps

• Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
• Verify your PR title matches the branch's Jira ticket ID
• Check that the Jira ticket exists and is accessible

This comment will be automatically deleted once the linter passes.